PowerShell

^{New 6.0.1.0}

Info

Learn how to utilize your own PowerShell scripts for custom monitoring, enabling end-users to execute them through self-service enabled Nodinite Monitor Views.

Execute virtually any PowerShell script
Utilize scripts for custom monitoring
Allow end-users to execute scripts as Remote Actions on-demand

Note

You must have WMF 5.1 or later.

This page outlines the monitoring aspects for the PowerShell Category in Nodinite, utilizing one or more role-based Monitor Views. Nodinite assesses system status based on user-defined thresholds, which can be set globally or for specific cases. To manage PowerShell effectively, remote commands are available as actions, allowing you to swiftly address any reported issues. Further details about the implemented Remote Actions are provided on this page.

Example with a list of monitored 'PowerShell' resources in a Monitor View

Monitoring Features

• A Nodinite Administrator must manually manage your PowerShell configurations. Sharing insights is very easy from within Nodinite using Monitor Views.
• State Evaluation - Based on simple logic (Write-Warning for Warnings, Write-Error for Errors)
• Category-based monitoring - To help you sort out the different types of resources, the monitored Resources are grouped by Categories

State evaluation for PowerShell based monitoring

The monitored PowerShell configurations are displayed within Nodinite as Resources. For example, if you have 2 Windows Source Server configurations with 2 and 3 PowerShell configurations, you will have 5 'PowerShell' resources in Nodinite.

• The name of the Resources are the same as the name for the PowerShell-configuration

• The 'PowerShell' resource belongs to the following Category:

  Category	Description
  PowerShell	Make sure the PowerShell configurations are within user-defined monitoring thresholds

  
  Here's an example with a List of Resources of the PowerShell Category in a Nodinite Monitor View.

• The Application name is the Display Name of the Windows Server:
  
  Here's an example using the Application filter option in a Nodinite Monitor View.

Each item (presents in Nodinite as a Resource) is evaluated with a state. (OK, Warning, Error, Unavailable).

From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.

Note

Depending on the user-defined synchronization interval set for the Windows Server Monitoring Agent, there might be a delay before Nodinite Web Client/Monitor Views reflects upon the change. Click the Sync All button (or on the dropdown for individual agent selection) to force Nodinite to request a resynchronization request.

Option to force Nodinite to request a resynchronization request with the Monitoring Agent.

PowerShell Monitoring

For the PowerShell category, the monitored state evaluates as described in the table below:

Remote Actions for PowerShell

The following Remote Actions are available for the PowerShell Category:

• Details
• Show Action Scripts

Here's an example of the PowerShell related Remote Actions.

Details

You can view some details for the selected PowerShell resource, click on the Action button and then clicking on the Details menu item within the 'Control Center' section.

To open the details modal, click the 'Details' action.

Next, click the option to present the modal.

Here's an example of the 'Details' modal.

Show Action Scripts

You can manage the alert thresholds for selected PowerShell resource, click on the Action button and then clicking on the Edit thresholds menu item within the 'Control Center' section.

To open the scripts modal, click the 'Show Action Scripts' action.

Next, click the option to present the modal.

Here's an example of the 'Action Scripts' modal.

Click on the Execute button to run the script on demand.

The user must confirm the intent to execute the script.

The output is presented at the bottom of the modal.

Here's an example of the result from the operation.

Configuration

Use the Remote Configuration to manage the PowerShell configuration.

PowerShell tab

Click the PowerShell tab to manage the PowerShell Monitoring options.

Here's an example of the 'PowerShell' configuration tab.

click the Add button to add a new entry, ultimately this will be the Resource as seen in Monitor Views.

PowerShell General tab

This is the Monitoring entry.

• Enabled - When checked, this PowerShell Script is monitored
• Display Name - The user-friendly name of this resource as provided to end-users within Monitor Views
• Description - User-friendly description for the PowerShell Script resource
• PowerShell Script - The script to use for the Monitoring
  
  Here's an example of the PowerShell configuration General tab.

User Action Scripts

This entry allows the System Administrator to provide a script collection end-users with allowance to execute content as Remote Actions.

Here's an example of the PowerShell User Script Collection tab.

click the Add button for each script to include in the script collection.

Here's an example of a PowerShell User Script entry.

PowerShell Authentication

Set authentication options executing the PowerShell script.

Here's an example of the PowerShell configuration Authentication tab.

Check the checkbox to execute the script on another target host.

• Is remote server - When checked, these PowerShell Scripts run on a remote server

  • Address - The address for the remote server

• Use authentication - When checked, authenticate to the remote server or impersonate a user locally via the username and password fields below

  • Domain User - The name of the Windows user account. Format: DOMAIN\User
  • Password - The password for the provided domain user

Here's an example of the PowerShell configuration Authentication fields.

Next Step

Add or manage Monitor View

Related

Windows Server Monitoring Agent
Resources
Monitoring
Monitor Views